…3111)

Adds the IPC plumbing for the onboarding telemetry blob to flow
client↔broker. Independent of PR #3088 (which adds the
recorder/store/constants); both are needed together for end-to-end
brokered onboarding telemetry.

Linked Feature:
[AB#3462876](https://identitydivision.visualstudio.com/fac9d424-53d2-45c0-91b5-ef6ba7a6bf26/_workitems/edit/3462876)
Linked PBI:
[AB#3568357](https://identitydivision.visualstudio.com/fac9d424-53d2-45c0-91b5-ef6ba7a6bf26/_workitems/edit/3568357)

| File | Change |
|---|---|
| `BrokerRequest.java` | Add `onboarding_seed_json` field (client →
broker) |
| `BrokerResult.java` | Add `onboarding_blob` field + builder + getter
(broker → client) |
| `InteractiveTokenCommandParameters.java` | Add `onboardingSeedJson`
field on the params builder |
| `AcquireTokenResult.java` | Add `onboardingBlob` field for carrying
the populated blob through the result chain |
| `MsalBrokerRequestAdapter.java` | Serialize `onboardingSeedJson` from
command parameters into `BrokerRequest` |
| `MsalBrokerResultAdapter.java` | Extract `onboardingBlob` from
`BrokerResult` into `AcquireTokenResult` |

All additions are pure data fields + adapter wiring. No behavior change
for existing callers (fields default to empty/null when not set).

- **Direction `client → broker`**: OneAuth/MSAL builds the seed JSON
(containing `sessionCorrelationId`, `onboardingMode`, `schema_version`)
and attaches it to the interactive request. The broker reads it via the
new field on `BrokerInteractiveTokenCommandParameters`, constructs its
own `OnboardingTelemetryRecorder` from the seed, and uses the same
correlation ID for its onboarding telemetry events.
- **Direction `broker → client`**: When the broker emits the populated
onboarding blob (after `finalizeBlob()`), it places it into
`BrokerResult.onboarding_blob`. The client extracts it into
`AcquireTokenResult.onboardingBlob`, where downstream OneAuth code reads
it and emits the blob through MATS.

See full design: [Mobile Onboarding Telemetry
Design](https://identitydivision.visualstudio.com/Engineering/_workitems/edit/3462876)
§6.6 (persistence and propagation) and §11.2 (broker → OneAuth blob
delivery).

- **Pairs with**: PR #3088 (`OnboardingTelemetryRecorder` +
`OnboardingTelemetryConstants` + `OnboardingSessionCorrelationStore`).
The recorder consumes the seed JSON read out of these IPC fields.
- **Consumers**:
- OneAuth:
[`shared/mobile-onboarding-android-fixes`](https://office.visualstudio.com/OneAuth/_git/OneAuth)
updates `BrokerRequestConverter` / `BrokerResultConverter` to read/write
these fields.
- Broker (`ad-accounts-for-android`):
`MsalAndroidBrokerCommandParameterAdapter` reads `onboardingSeedJson`;
broker error handler / SSO controller will write `onboarding_blob` once
the recorder lifecycle is wired (separate PBI,
[AB#3568359](https://identitydivision.visualstudio.com/fac9d424-53d2-45c0-91b5-ef6ba7a6bf26/_workitems/edit/3568359)).
- **No breaking changes**: all new optional fields, no modifications to
existing serialization order or field semantics.

- Round-trip serialization is exercised by existing `BrokerRequest` /
`BrokerResult` tests (Gson + Bundle); new fields default to empty/null
when not set, so no existing test should regress.
- E2E validated locally via OneAuth `local-only-onboarding-telemetry`
branch + a combined Common build (`mavenLocal` `0.0.0-zhipan-mot-7`):
seed JSON flows OneAuth → BrokerRequest → broker → BrokerResult →
OneAuth.

…lemetry, Fixes AB#3462876 (#3117)

Adds the remaining step ID and blocking error constants from the Mobile
Onboarding Telemetry design (section 9 Step Taxonomy) to
`OnboardingTelemetryConstants`. Pure additive - no behavior change, no
caller wiring in this PR.

Linked Feature:
[AB#3462876](https://identitydivision.visualstudio.com/fac9d424-53d2-45c0-91b5-ef6ba7a6bf26/_workitems/edit/3462876)

PR #3088 shipped the recorder + the 5 step/blocking-error constants
OneAuth needed for non-brokered (`STEP_AUTHENTICATION_STARTED`,
`STEP_BROKER_INSTALL_PROMPTED`, `STEP_DEVICE_REGISTRATION_STARTED`,
`BLOCKING_ERROR_BROKER_INSTALL`, `BLOCKING_ERROR_MDM_FLOW`). The
remaining ~20 step IDs from the design will be needed by:

- The WebView hooks PR (follow-up) - emits `MDMEnrollmentStarted`,
`CompanyPortalLaunched`, `WebCpEnrollmentStarted`, etc. from
`AzureActiveDirectoryWebViewClient` URL-handler sites.
- Broker-side step emission (follow-up) - `AccountSelectionStarted`,
`InterruptFlowStarted`, `PrtAcquired`, `TokenIssued`, etc.
- OneAuth follow-ups for AM API + WebCP detection (Veena's request) -
needs `MDMEnrollmentStarted` constant.
- Termination steps - `UserCanceled`, `AuthorizationTimedOut`.

Landing the constants ahead of caller wiring lets downstream PRs
reference typed constants instead of hardcoded strings, and avoids a
chicken-and-egg sequencing problem.

Grouped by onboarding flow phase (matching design section 9):

- **Authentication / WebView**: `STEP_ACCOUNT_SELECTION_STARTED`,
`STEP_PASSKEY_AUTH_STARTED`, `STEP_CERT_BASED_AUTH_STARTED`
- **MFA / Strong Auth**: `STEP_STRONG_AUTH_SETUP_STARTED`,
`STEP_STRONG_AUTH_SETUP_COMPLETED`,
`STEP_AUTHENTICATOR_MFA_LINKING_STARTED`
- **CA Block & Remediation**: `STEP_CA_BLOCK_RECEIVED`,
`STEP_INTERRUPT_FLOW_STARTED`, `STEP_CONSENT_PROMPT_SHOWN`,
`STEP_TERMS_OF_USE_SHOWN`, `STEP_PASSWORD_RESET_REQUIRED`
- **Device Registration**: `STEP_DEVICE_REGISTRATION_UPGRADE_STARTED`
- **MDM Enrollment**: `STEP_MDM_ENROLLMENT_STARTED` (value
`MDMEnrollmentStarted`), `STEP_COMPANY_PORTAL_LAUNCHED`,
`STEP_WEB_CP_ENROLLMENT_STARTED`, `STEP_GOOGLE_ENROLLMENT_STARTED`
- **Intune App Protection**: `STEP_INTUNE_APP_PROTECTION_REQUIRED`
- **Compliance Remediation**: `STEP_COMPLIANCE_REMEDIATION_STARTED`,
`STEP_COMPLIANCE_REMEDIATION_COMPLETED`
- **Token Acquisition**: `STEP_PRT_ACQUIRED`, `STEP_TOKEN_ISSUED`
- **Termination**: `STEP_USER_CANCELED`, `STEP_AUTHORIZATION_TIMED_OUT`
- **Blocking error**: `BLOCKING_ERROR_DEVICE_REGISTRATION`
(`"DEVICE_REGISTRATION_REQUIRED"`)

All values are PascalCase (consistent with the existing `STEP_*`
constants and matching what eSTS/MATS expect for these enum-like step
values).

- No new tests - pure constant additions; existing
`OnboardingTelemetryRecorderTest` and
`OnboardingSessionCorrelationStoreTest` continue to pass.
- Built locally; constants compile cleanly.

- **Builds on**: PR #3088 (already merged) - extends
`OnboardingTelemetryConstants` added there.
- **Consumed by** (follow-up PRs):
- WebView page-tracking hooks (`AzureActiveDirectoryWebViewClient`
setter + emissions)
- Broker step emission (`BrokerSsoController`, `PrtController`, error
handler)
- OneAuth caller updates (AM API + WebCP detection per Veena's PR #3088
comment)
- **No breaking changes** - purely additive to the existing `object`.